Mobile Device Workload Management for Cloud Computing Using SIP And Presence To Control Workload And Method Thereof

ABSTRACT

A method is implemented in a computer infrastructure having computer executable code tangibly embodied on a computer readable storage medium having programming instructions. The programming instructions are operable to manage workload for cloud computing by transferring workload to at least one mobile device using Session Initiation Protocol (SIP).

FIELD OF THE INVENTION

The present invention generally relates to a system and method ofworkload management for cloud computing using SIP and presence and, moreparticularly, a system and method of mobile device workload managementfor cloud computing using SIP and presence to control workload andmethod thereof.

BACKGROUND

Cloud computing is a means of providing service delivery for consumerand business needs in a simplified way, providing unbounded scale anddifferentiated quality of service. Businesses are looking to cloudcomputing to foster rapid innovation and decision making, for theagility needed to respond quickly in today's highly competitiveenvironment, to reduce capital and operational costs, and an environmentthat scales easily to effectively meet customer needs.

Cloud computing enables organizations to provide reliable, on-demandservices in a flexible and affordable manner offering the benefits ofopen standards, scalable systems and service oriented architecture. Withthese benefits also come new complexities that must be properly managed.These complexities include, for example,

-   -   Rapid growth of virtualized resources across multiple        environments;    -   Relationship of virtualized resources to underlying physical        infrastructure; and    -   Health monitoring and problem determination across a physical        and virtualized infrastructure.

In particular, cloud computing is a way of computing, via the Internet,that broadly shares computer resources instead of using software orstorage on a local PC. Typical cloud computing providers deliver commonbusiness applications online which are accessed from a web browser on apersonal computer, while the software and data are stored on servers.This is a constraint of the current paradigm of cloud computinginfrastructure which consists of reliable services delivered throughdata centers and built on servers which perform the processingrequirements, to be accessed by the web browser, for example, on apersonal computer.

In general, cloud computing customers do not own the physicalinfrastructure, instead avoiding capital expenditure by renting usagefrom a third-party provider. They consume resources as a service and payonly for resources that they use. This, though, requires a server layerwhich consists of computer hardware and/or computer software productsthat are specifically designed for the delivery of cloud services,including multi-core processors, cloud-specific operating systems andcombined offerings. During heavy workloads or demand, this can place astrain on the servers, slowing services.

Accordingly, there exists a need in the art to overcome the deficienciesand limitations described herein above.

BRIEF SUMMARY

In a first aspect of the invention, a method is implemented in acomputer infrastructure having computer executable code tangiblyembodied on a computer readable storage medium having programminginstructions. The programming instructions are operable to manageworkload for cloud computing by transferring workload to at least onemobile device using Session Initiation Protocol (SIP).

In another aspect of the invention, a method is implemented on acomputer infrastructure having hardware. The method comprises: receivingregistration information of a mobile device using SIP registration;sending a workload request to the mobile device based on theregistration; and providing computing work to the mobile device from acontent cache associated with a cloud fabric, based on the workloadrequest, for assisting in cloud computing.

In an additional aspect of the invention, a computer program productcomprising a computer usable storage medium having readable program codeembodied in the medium is provided. The computer program productincludes at least one component operable to: provision a network as anSIP device in an Home Subscriber Server (HSS) and IP MultimediaSubsystem (IMS) network; pre-provision a content service with specificcontext and data that cloud clients require; provision a cloud fabricwith details of the mobile device; and provision the mobile device witha lightweight presence client that can use an IMS stack found on mobileplatforms.

In a further aspect of the invention, a computer system for provisioningcomponents. The system comprises a CPU, a computer readable memory and acomputer readable storage media. Additionally, the system comprises:first program instructions to provision a network as an SIP device in aHome Subscriber Server (HSS) and IP Multimedia Subsystem (IMS) network;second program instructions to pre-provision a content service withspecific context and data that cloud clients require; third programinstructions to provision a cloud fabric with details of the mobiledevice; and fourth program instructions to provision the mobile devicewith a lightweight presence client that can use an IMS stack found onmobile platforms. The program instructions are stored on the computerreadable storage media for execution by the CPU via the computerreadable memory.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The present invention is described in the detailed description whichfollows, in reference to the noted plurality of drawings by way ofnon-limiting examples of exemplary embodiments of the present invention.

FIG. 1 an illustrative environment for implementing the steps inaccordance with aspects of the invention;

FIG. 2 shows an exemplary flow in accordance with aspects of theinvention;

FIG. 3 illustrates a high level block diagram and/or process flow inaccordance with aspects of the invention; and

FIG. 4 shows an architecture overview in accordance with aspects of theinvention.

DETAILED DESCRIPTION

The present invention generally relates to a system and method ofworkload management for cloud computing using Session InitiationProtocol (SIP) and presence and, more particularly, to a system andmethod of mobile device workload management for cloud computing usingSIP and presence to control workload and method thereof. Morespecifically, the present invention provides significant opportunitiesfor increasing the efficiency of clouds by allowing for adhoc leveragingof computing power in nodes that are not formally part of the cloudalready.

SIP is a signaling protocol used for controlling multimediacommunication sessions such as voice and video calls over InternetProtocol (IP). The protocol can be used for creating, modifying andterminating two-party (unicast) or multiparty (multicast) sessionsconsisting of one or several media streams. Other application examplesinclude video conferencing, streaming multimedia distribution, instantmessaging, and presence information. The SIP protocol is a TCP/IP-basedApplication Layer protocol. SIP is designed to be independent of theunderlying transport layer; it can run on Transmission Control Protocol(TCP), User Datagram Protocol (UDP), or Stream Control TransmissionProtocol (SCTP).

In embodiments, the system and method of the present invention allowsfor clouds to use telecommunications based signaling to use SIP totransfer workloads to mobile devices (e.g., 2G mobile devices, 3Gdevices, netbooks, etc.) that are tethered to networks in anintermittently or constantly connected fashion. For example, inimplementation, the present invention can add a mobile device to apublic or private cloud. The present invention can send work to themobile device and then dissociate the mobile device from the cloud byleveraging IMS network based SIP signaling. Thus, in embodiments, thepresent invention leverages SIP based signaling to bring mobileendpoints into clouds or dissociate the mobile devices. In additionalembodiments, the present invention supports an intensive locationcompute or 3D compute where data is not on the cloud, but on the mobiledevice or other third party device.

The IMS reference architecture is a standard in many mobile (and fixed)telecommunications' devices. Wireless networks are also rapidlyimproving, allowing for the easy download and upload of significantamounts of data to the mobile device. In addition, handsets (hereinafterreferred generally as mobile devices) are significantly improving inorder to facilitate the present invention. For example, mobile devicesare exhibiting significantly more processing power by using higher endprocessors from specialized mobile device vendors that permit activemulti-tasking, while still continuing to optimize battery life. Inaddition, mobile devices have significant memory capabilities, andimproved battery life allowing for more efficient computing to continuefor longer periods of time. Mobile devices include radios for high speeddata (e.g., EVDO variants, Wimax (802.16e), Wifi (802.11x), LTE, inaddition to on board Assisted GPS chipsets allowing for location basedcomputing to occur locally.

In addition, chipsets being used in the next generation mobile devicesare the same as those being used for much more powerful netbooks andother computing devices. Also, there is a significant increase in IMSnetworks, leveraging SIP client stacks that are being bundled by themobile device vendor. It is also known that in any 24 hour cycle, mobiledevices have long periods where they essentially are idle and will havecompute cycles available, but have largely been hitherto ignored andunutilized. Also, the RPID and PIDF formats in presence servers can belogically extended to include multiple additional elements as describedherein, in addition to the fact that large slices of time remain whenmobile devices are turned off and charging without being used on activedata sessions or voice calls (e.g., during night time).

In view of the above, the present invention focuses on deliveringpriority on a call by call basis using callee controlled white-lists,allowing for the required privacy in implementing such a solution. Thepresent invention also works across IP as well as SS7 and existingtelecommunications networks, in addition to factoring in location andtime of day intervals to determine and provide priority to the mobiledevices for management of workload on a computing cloud. The presentinvention also uses a feature code based approach for IN (IntelligentNetwork) infrastructure, and fosters IMS based backplanes as itleverages SIP based signaling to bring mobile endpoints into clouds anddissociate from the clouds. The present invention also suits and scalescloud offerings which essentially have unique characteristic and differfrom traditional grids.

The present invention also provides infrastructure extensions, inclusiveof a lightweight presence enabled cloud client, that allows for a mobiledevice to be added to a public or private cloud, which can send work(e.g., workload management) to the mobile device and then dissociate themobile device from the cloud by leveraging IMS network based SIPsignaling. Additionally, the use of a network housed presence server isprovided as a set of trigger points to initiate interactions between thecloud and the mobile device.

The present invention also accounts for a growing (but yet unnoticed)trend of high powered mobile devices, which essentially sit idle for alarge amounts of time, and allows for these devices to become adhocparticipants in cloud infrastructures. For example, in implementation,the idle mobile devices may be used to process data for the cloud. Thisis accomplished using SIP signaling semantics (which is used for settingup, controlling and dismantling media rich communications sessionsonly).

In addition, the present invention effectively leverages futuremigration, by leveraging SIP based signaling to bring mobile endpointsinto clouds and dissociate using SIP based signaling. The costs savingsassociated with using the present invention is significant given theexploding number of high power mobile form factors in the market and thefact that significant amount of the day exists where these devices arelargely idle. Several applications also exist where workload can beoffloaded from the cloud for dissociated processing which is supportedby the present invention.

System Environment

As will be appreciated by one skilled in the art, the present inventionmay be embodied as a system, method or computer program product.Accordingly, the present invention may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,the present invention may take the form of a computer program productembodied in any tangible medium of expression having computer-usableprogram code embodied in the medium.

Any combination of one or more computer usable or computer readablemedium(s) may be utilized. The computer-usable or computer-readablemedium may be, for example but not limited to, an electronic, magnetic,optical, electromagnetic, infrared, or semiconductor system, apparatus,device, or propagation medium. More specific examples (a non-exhaustivelist) of the computer-readable medium would include the following:

-   -   an electrical connection having one or more wires,    -   a portable computer diskette,    -   a hard disk,    -   a random access memory (RAM),    -   a read-only memory (ROM),    -   an erasable programmable read-only memory (EPROM or Flash        memory),    -   an optical fiber,    -   a portable compact disc read-only memory (CDROM),    -   an optical storage device,    -   a transmission media such as those supporting the Internet or an        intranet, or    -   a magnetic storage device.

The computer-usable or computer-readable medium could even be paper oranother suitable medium upon which the program is printed, as theprogram can be electronically captured, via, for instance, opticalscanning of the paper or other medium, then compiled, interpreted, orotherwise processed in a suitable manner, if necessary, and then storedin a computer memory.

In the context of this document, a computer-usable or computer-readablemedium may be any storage medium that can contain, store, communicate,propagate, or transport the program for use by or in connection with theinstruction execution system, apparatus, or device. The computer-usablestorage medium may include a propagated data signal with thecomputer-usable program code embodied therewith, either in baseband oras part of a carrier wave. The computer usable program code may betransmitted using any appropriate medium, including but not limited towireless, wireline, optical fiber cable, RF, etc.

Computer program code for carrying out operations of the presentinvention may be written in any combination of one or more programminglanguages, including an object oriented programming language such asJava, Smalltalk, C++ or the like and conventional procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The program code may execute entirely on the user's computer,partly on the user's computer, as a stand-alone software package, partlyon the user's computer and partly on a remote computer or entirely onthe remote computer or server. In the latter scenario, the remotecomputer may be connected to the user's computer through any type ofnetwork. This may include, for example, a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

FIG. 1 shows an illustrative environment 10 for managing the processesin accordance with the invention. To this extent, the environment 10includes a server or other computing system 12 that can perform theprocesses described herein in a cloud environment. In embodiments, theserver can be a “cloud” server, which allows processing to be performedby a mobile device as discussed herein. In embodiments, the server 12includes a computing device 14. The computing device 14 can be residenton a network infrastructure or computing device of a third party serviceprovider (any of which is generally represented in FIG. 1).

The computing device 14 also includes a processor 20, memory 22A, an I/Ointerface 24, and a bus 26. The memory 22A can include local memoryemployed during actual execution of program code, bulk storage, andcache memories which provide temporary storage of at least some programcode in order to reduce the number of times code must be retrieved frombulk storage during execution. In addition, the computing deviceincludes random access memory (RAM), a read-only memory (ROM), and anoperating system (O/S). The memory (e.g., 22A) may store businessintelligence, data mining, regression analysis and/or modeling andsimulation tools for execution by the processor 20.

The computing device 14 is in communication with the external I/Odevice/resource 28 and the storage system 22B. For example, the I/Odevice 28 can comprise any device that enables an individual to interactwith the computing device 14 (e.g., user interface) or any device thatenables the computing device 14 to communicate with one or more othercomputing devices using any type of communications link. The externalI/O device/resource 28 may be for example, a handheld device, PDA,mobile device, keyboard etc.

In general, the processor 20 executes computer program code (e.g.,program control 44), which can be stored in the memory 22A and/orstorage system 22B. Moreover, in accordance with aspects of theinvention, the program control 44 can implement the processes of thepresent invention. The processor 20 can be implemented as one or moreprogram code in the program control 44 stored in memory 22A as separateor combined modules. Additionally, processor 20 may be implemented asseparate dedicated processors or a single or several processors toprovide the function of the present invention. A processor can also beresident or part of a presence server (A/S)/IMS network 50, applicationserver 60, or content provider 80 for example.

In implementation, a mobile device (external I/O device/resource 28)registers with network (e.g., server) 10 using standard IMS semanticsvia a SIP registration, as well as registering with the presence serverA/S 50 as a client. The mobile device can also register as a watcher forincoming cloud changes. The device information is sent to a cloud fabric70 (which may be associated with or completely resident on the server)by the presence server A/S 50. The cloud processes this information touse as a basis for future decisions. The cloud fabric 70 sends aworkload request to the mobile device, which is sent in the form of apresence notification to the mobile device. The mobile device performscomputing work after downloading anything it may need from the contentcache, from the content provider 80. Upon termination or conclusion,results go back to the cloud fabric, and the cloud fabric may initiatedissociation of the mobile device. It should be understood by those ofskill in the art that, in embodiments, the presence server (A/S)/IMSnetwork 50, application server 60, or content provider 80, for example,may be represented by or resident on the server 10.

In this way, the present invention leverages the IMS infrastructure inthe evolving network domain in a unique way to support cloud computing.The present invention also provides a highly feasible, low cost ofimplementation to integrate mobile devices into the cloud, usingpresence as an indicator of a mobile devices ability to accept workload.The use of presence in determining if a mobile device has entered orleft the cloud also allows the cloud fabric the ability to resend workto available nodes of a mobile device as it becomes disconnected.

While executing the computer program code, the processor 20 can readand/or write data to/from memory 22A, storage system 22B, and/or I/Ointerface 24. The program code executes the processes of the invention.The bus 26 provides a communications link between each of the componentsin the computing device 14.

The computing device 14 can comprise any general purpose computingarticle of manufacture capable of executing computer program codeinstalled thereon (e.g., a personal computer, server, etc.). However, itis understood that the computing device 14 is only representative ofvarious possible equivalent-computing devices that may perform theprocesses described herein. To this extent, in embodiments, thefunctionality provided by the computing device 14 can be implemented bya computing article of manufacture that includes any combination ofgeneral and/or specific purpose hardware and/or computer program code.In each embodiment, the program code and hardware can be created usingstandard programming and engineering techniques, respectively.

Similarly, the computing infrastructure 12 is only illustrative ofvarious types of computer infrastructures for implementing theinvention. For example, in embodiments, the server 12 comprises two ormore computing devices (e.g., a server cluster) that communicate overany type of communications link, such as a network, a shared memory, orthe like, to perform the process described herein. Further, whileperforming the processes described herein, one or more computing deviceson the server 12 can communicate with one or more other computingdevices external to the server 12 using any type of communications link.The communications link can comprise any combination of wired and/orwireless links; any combination of one or more types of networks (e.g.,the Internet, a wide area network, a local area network, a virtualprivate network, etc.); and/or utilize any combination of transmissiontechniques and protocols.

Flow Diagram

FIGS. 2 and 3 show exemplary flows for performing aspects of the presentinvention. The steps of FIGS. 2 and 3 may be implemented in theenvironment of FIG. 1, for example. The flow diagrams may equallyrepresent a high-level block diagram or a swim-lane diagram of theinvention. The flowchart and/or block diagrams in FIGS. 2 and 3 (and anyother flowcharts and/or block diagrams) illustrates the architecture,functionality, and operation of possible implementations of systems,methods and computer program products according to various embodimentsof the present invention. In this regard, each block in any of theflowcharts, block diagrams or swim-lane diagrams may represent a module,segment, or portion of code, which comprises one or more executableinstructions for implementing the specified logical function(s). Itshould also be noted that, in some alternative implementations, thefunctions noted in the blocks may occur out of the order noted in thefigure. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Each block of each flowchart, and combinations of theflowchart illustration can be implemented by special purposehardware-based systems that perform the specified functions or acts, orcombinations of special purpose hardware and computer instructionsand/or software, as described above. Moreover, the steps of the flowdiagram may be implemented and executed from either a server, in aclient server relationship, or they may run on a user workstation withoperative information conveyed to the user workstation. In anembodiment, the software elements include firmware, resident software,microcode, etc.

In embodiments, a service provider, such as a Solution Integrator, couldoffer to perform the processes described herein. In this case, theservice provider can create, maintain, deploy, support, etc., thecomputer infrastructure that performs the process steps of the inventionfor one or more customers. These customers may be, for example, anybusiness that uses technology. In return, the service provider canreceive payment from the customer(s) under a subscription and/or feeagreement and/or the service provider can receive payment from the saleof advertising content to one or more third parties.

Furthermore, the invention can take the form of a computer programproduct accessible from a computer-usable or computer-readable mediumproviding program code for use by or in connection with a computer orany instruction execution system. The software and/or computer programproduct can be implemented in the environment of FIG. 1. For thepurposes of this description, a computer-usable or computer readablemedium can be any apparatus that can contain, store, communicate,propagate, or transport the program for use by or in connection with theinstruction execution system, apparatus, or device. The medium can be anelectronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system (or apparatus or device) or a propagation medium.Examples of a computer-readable storage medium include a semiconductoror solid state memory, magnetic tape, a removable computer diskette, arandom access memory (RAM), a read-only memory (ROM), a rigid magneticdisk and an optical disk. Current examples of optical disks includecompact disk-read only memory (CD-ROM), compact disc-read/write (CD-R/W)and DVD.

FIG. 2 depicts an exemplary flow for a process in accordance withaspects of the present invention. The flow process of FIG. 2 may beperformed over several players (actors) such as, for example, a mobiledevice, a presence server (A/S)/IMS network, content download server,application server and a cloud fabric. More specifically, at step 200,the mobile device registers with the network using standard IMSsemantics via a SIP Registration. This process step assumes the usualIFC (Initial Filter Criteria) process with the IMS core; although, otherimplementations are contemplated by the present invention.

At step 205, the mobile device registers with the presence server (A/S)as a client. The mobile device can also register as a watcher forincoming cloud changes. The mobile device sends registration information(SIP Publish) to the presence server A/S. This information may include,for example, any combination of device status, applications running,utilization information, time of day availability and/or other suchinformation including location and presence. The information can bepackaged into a standard presence document, which the presence server(A/S) is capable of interpreting the information.

At step 210, the mobile device information is sent to the cloud fabricby the presence server (A/S). At step 215, the cloud fabric processesthis information to use as a basis for future decisions, e.g., workloadmanagement. The mobile device can also periodically send state changesto the cloud fabric via the presence server (A/S). An example of a statechange could be “turn on airplane mode for a period of time” orutilization has dropped below a certain critical point. Other examples,which should not be considered limiting features, include data radioturned on, or geographic location entered (e.g., user is at home anddevice will be idle). At step 220, the presence server (A/S) notifiesthe cloud fabric about these changes (changes in the presence documentessentially)

At step 225, the cloud fabric sends a workload request to the mobiledevice, which is sent in the form of a presence notification to themobile device. Simultaneously, processing instructions and content areuploaded by the cloud fabric to a content cache (e.g., at a contentdownload server) on the edge of the network. At step 230, the mobiledevice performs computing work after downloading anything it may needfrom the content cache. Upon termination or conclusion, results go backto the cloud fabric (if necessary via the presence server (A/S) (statechanges) or via the content cache) and the cloud fabric may initiatedissociation of the mobile device, at step 235. At step 240, accountingrecords as necessary are generated and maintained. The cloud can thenrevert back to its original state. In this way, the there is an increasein the efficiency of clouds by allowing for adhoc leveraging ofcomputing power in nodes (mobile devices) that are not formally part ofthe cloud.

In FIG. 3, steps are shown for the provisioning of the mobile deviceinto the cloud fabric and the telecommunications IMS network. Inembodiments, the provisioning process can be carried out using aprovisioning workflow. For example, at step 300, the network isprovisioned as any SIP device would be, in the Home Subscriber Server(HSS) and the IP Multimedia Subsystem (IMS) network. In addition,specific information for using the presence server can be provisionedusing existing IMS provisioning semantics. At step 305, the contentservice is pre-provisioned with specific context and data that the cloudclients may require. At step 310, the cloud fabric is provisioned withall the details of the mobile device, such as its capabilities, specificavailability times, processing information, processing threshold, etc.At step 315, the mobile device is provisioned with a lightweightpresence client that can use the IMS stack found on mobile platforms.The client periodically communicates with the presence server A/S in thenetwork and the cloud fabric and content server(s) as necessary.

Architecture of the Present Invention

FIG. 4 shows the architecture overview of the present invention. Inparticular, FIG. 4 shows a device and access domain 400, a wirelesscarrier domain 440 and an enterprise cloud domain 470. The device andaccess domain 400 includes a mobile device 405 (e.g., cloud participant)and network antennae 410, for example. The wireless carrier domain 440includes an IMS core 415. The IMS core 415 may include, for example, ahome subscriber server database, a call session control function stack,as well as a edge download server and a converged SIP A/S module. Theenterprise cloud domain 470 includes a private public cloudinfrastructure 475, which may include a cloud bus fabric between aplurality of cloud nodes, and a database having, for example, a cloudprofile, service profile, device profile and state data, all of whichwere discussed above.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims, if applicable, areintended to include any structure, material, or act for performing thefunction in combination with other claimed elements as specificallyclaimed. The description of the present invention has been presented forpurposes of illustration and description, but is not intended to beexhaustive or limited to the invention in the form disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The embodiment was chosen and described in order to best explain theprincipals of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated. Accordingly, while the invention has beendescribed in terms of embodiments, those of skill in the art willrecognize that the invention can be practiced with modifications and inthe spirit and scope of the appended claims.

What is claimed is:
 1. A computer program product comprising anon-transitory computer readable storage medium or device having programinstructions embodied therewith, the program instructions executable bya computing device to cause the computing device to: receiveregistration information of a mobile device with a IP multimediasubsystem (IMS) network using IMS semantics via a Session InitiationProtocol (SIP) registration process; receive registration information ofa mobile device with a presence server using information packaged in apresence document, wherein the presence document comprises device statusand presence of the mobile device; process the presence document at adistributed network for future workload management decisions; manageworkload for distributed network computing by utilizing the processedpresence document to determine whether the mobile device is available toprocess the workload; send via the IMS network using SIP a workloadrequest in the form of a presence notification to the mobile devicebased on the registration, wherein the presence notification includesdata for retrieving the workload and provides for ad hoc leveraging ofcomputing power from the mobile device, which was not formally part ofthe distributed network prior to receiving the presence notification;upload instructions and content for the workload to a content cache bythe distributed network; provide the instructions and content for theworkload to the mobile device from the content cache associated with thedistributed network, based on the workload request, for assisting in thedistributed network computing; and perform the workload on the mobiledevice after the providing the workload from the content cache to themobile device.
 2. The computer program product of claim 1, wherein thepresence server receives the registration information from the mobiledevice.
 3. The computer program product of claim 2, wherein the presencedocument further comprises applications running, utilizationinformation, time of day availability, and location.
 4. The computerprogram product of claim 1, wherein the registration information is sentto the distributed network by the presence server for processing thefuture workload management decisions.
 5. The computer program product ofclaim 1, further comprising program instructions executable by thecomputing device to cause the computing device to periodically receivestate changes of the mobile device via the presence server.
 6. Thecomputer program product of claim 1, wherein the distributed networksends the workload request to the mobile device, which is sent via thepresence notification to the mobile device.
 7. The computer programproduct of claim 6, further comprising program instructions executableby the computing device to cause the computing device to simultaneouslysend the workload request to the mobile device and upload theinstructions and content by the distributed network to the content cacheon an edge of the distributed network.
 8. The computer program productof claim 7, wherein the content cache uploads the instructions andcontent for the workload to the mobile device for performing theworkload.
 9. The computer program product of claim 1, further comprisingprogram instructions executable by the computing device to cause thecomputing device to initiate dissociation of the mobile device from thedistributed network.
 10. The computer program product of claim 1,wherein the management of the workload includes adhoc leveraging ofcomputing power using at least one mobile device which is not formallypart of the distributed network computing.
 11. The computer programproduct of claim 10, wherein the management of the workload includesusing telecommunications based signaling to transfer workloads to the atleast one mobile device that is tethered to the distributed networkcomputing in an intermittently or constantly connected fashion.
 12. Thecomputer program product of claim 1, wherein the program instructionsexecutable by the computing device are further operable to cause thecomputing device to dissociate the at least one mobile device from thedistributed network computing by leveraging IMS network based SIP. 13.The computer program product of claim 1, wherein the workload managementworks across IP and SS7 telecommunications networks.
 14. The computerprogram product of claim 1, wherein the program instructions executableby the computing device are further operable to factor in location andtime of day intervals to determine and provide priority to the at leastone mobile device that will assist in the workload management.
 15. Thecomputer program product of claim 1, wherein the program instructionsexecutable by the computing device are further operable to use networkhoused presence server points to initiate interactions between thedistributed network computing and the at least one mobile device.